PROFINET IO-Controller V3

Version V3.3.0.12

Bugs:

• PSPNMV3-627: Missing check for record data length on legacy Write \ Read record services
• PSPNMV3-625: Netload certification tests "Faulty operation" for netload class III fail

Version V3.3.0.11

Changes:

• PSPNMV3-615: Add DPM Mailbox fragmentation support to service PNM_AP_CMD_CFG_RECORD_REQ
• PSPNMV3-613: Upgrade Profinet Core to V1.6.0.8
• PSPNMV3-598: Update CTLDINA to tolerate lost ARP response

Bugs:

• PSPNMV3-612: Sometimes wrong diagnosis status in Get Slave Connection Info service reported
• PSPNMV3-604: No ARP requests are send by IO Controller
• PSPNMV3-594: Dead-lock on AR Release during failed RPC Request

Version V3.3.0.10

Changes:

• PSPNMV3-580: Upgrade Profinet Core to V1.6.0.7

Bugs:

• PSPNMV3-581: Upgrade lwIP based IP stack to V4.1.0.9
• PSPNMV3-574: sometimes unexpected AR abort when establishing a lot of ARs in parallel

Version V3.3.0.9

Changes:

• PSPNMV3-564: Upgrade Profinet Core to V1.6.0.6

Bugs:

• PSPNMV3-567: Valid Configure Submodule request rejected
• PSPNMV3-563: Unexpected loss of cyclic communication to IO Devices connected to Ethernet port 2
• PSPNMV3-561: Invalid memory access on link status change
• PSPNMV3-547: Communication not established when switching bus state to on after loading remanent data.

Version V3.3.0.8

Changes:

• PSPNMV3-545: Upgrade component Profinet Core to V1.6.0.5

Bugs:

• PSPNMV3-543: API Change for Diagnosis Indication: Improper decoding of Qualified Channel Diagnosis
• PSPNMV3-542: Unexpected timeout error when using Get Device Info service

Version V3.3.0.7

Changes:

• PSPNMV3-540: Update component Profinet Core to V1.6.0.4
• PSPNMV3-536: In the DPM startup parameters, add a flag to disable/enable the NetIdent feature.

Bugs:

• PSPNMV3-539: IO Contoller crashs when NDIS is enabled and NetLoad test is executed
• PSPNMV3-532: no API exists to generate PDPortMRPDataAdjust record in blockversion 1.1

Version V3.3.0.6

Bugs:

• PSPNMV3-529: [loadable module]: use unique identifiers for all kinds of hardware objects
• PSPNMV3-528: The transfer sequence of record data during the parameterization phase does not meet the specification.
• PSPNMV3-525: Wrong mode used in FSParameterBlock

Version V3.3.0.5

Changes:

• PSPNMV3-524: Register Profinet Interface EndPoint when the network state is changed to "NetworkUp"
• PSPNMV3-523: Update to LLDP V5.2.0.3
• PSPNMV3-518: Update component Profinet Core to V1.6.0.3

Bugs:

• PSPNMV3-519: TED conformance check failes due missing SNMP Mib entries

Version V3.3.0.4

Changes:

• PSPNMV3-517: Update Profinet Core to V1.6.0.2

Bugs:

• PSPNMV3-515: Old or inconsistent output data sent

Version V3.3.0.3

Bugs:

• PSPNMV3-512: IP address not reset when DCP Factory Reset received

Version V3.3.0.2

Bugs:

• PSPNMV3-510: If user requests a WriteRecord with data length 0 firmware gets stuck in endless loop and can no longer be accessed via DPM
• PSPNMV3-505: Invalid encoding of PDInterfaceMRPDataAdjust V1.1 record

Version V3.3.0.1

Bugs:

• PSPNMV3-504: Unexpected IP address conflict detection match
• PSPNMV3-503: Legacy Bus Scan Method might return wrong device information
• PSPNMV3-499: Unexpected packet length for failed Read Implicit Record service response
• PSPNMV3-498: Update PSPNCORE to V1.6.0.1
• PSPNMV3-496: The usQualifier values in DCP Set IP and Set Name requests are unverified by the stack.
• PSPNMV3-493: Invalid packet length for Get IOD Configuration service confirmation

Version V3.3.0.0

New Features:

• PSPNMV3-443: Add support for NDIS for loadable modules
• PSPNMV3-399: Feature: Allow to read PDRealData on local Port- and Interfacesubmodules
• PSPNMV3-395: Feature: Add taglist to modify firmware identification parameters
• PSPNMV3-337: Add check for mixed multiple interface mode
• PSPNMV3-313: Add support for netX4000 chip
• PSPNMV3-159: feature: add NDIS in DPM channel 1

Changes:

• PSPNMV3-492: update to EthernetInterface V4.5.0.1
• PSPNMV3-455: Integrate external PSEIF V4.5.0.0
• PSPNMV3-452: Update PSPNCORE external to V1.6.0.0
• PSPNMV3-450: Update PSTBHAL to V1.2.0.0
• PSPNMV3-447: update to rcX V2.1.11.11
• PSPNMV3-446: update to DRVETH V1.5.0.0
• PSPNMV3-444: DCP Identify Response field IPOptions.BlockInfo shall be ignored
• PSPNMV3-433: Update PSCFGMGR to V1.2.0.0
• PSPNMV3-430: RCX_UNREGISTER_APP_REQ is not accepted by firmware in some cases (e.g. using TCP Server)
• PSPNMV3-429: Update PSLLDPV5 to V5.2.0.2
• PSPNMV3-424: move Socket API handling from DPM Channel 0 to DPM Channel 1
• PSPNMV3-404: update to ConfigManager V1.0.2.0
• PSPNMV3-378: Introduce timeout for IRT startup
• PSPNMV3-364: add a new flag that is set in case a submodule with diagnosis is reported in ModuleDiffBlock
• PSPNMV3-354: configuration packets with higher StructVersion shall be acceptedby the firmware if technically possible

Bugs:

• PSPNMV3-491: Invalid FrameSendOffset in IOCR block for non IRT IOCR
• PSPNMV3-486: IP address conflict not cleared by Channel Init or Start Stop Communication service
• PSPNMV3-482: Wrong SlaveState (OK) in MasterStatusBlock if an IO Device has reported a fault
• PSPNMV3-479: Service DCP Get is rejected if MAC Address shall be read
• PSPNMV3-477: sometimes no LinkStatus Indication generated to registered application on LinkDown
• PSPNMV3-476: Sometimes COM-Flag not cleared even when all network cables are removed
• PSPNMV3-475: Get basic parameter service returns wrong DPM Watchdog time
• PSPNMV3-474: Some Alarm Acknowledge Request parameters are not checked for plausability
• PSPNMV3-473: Reject Alarm Acknowledge Request before Alarm Response
• PSPNMV3-471: Invalid led state and Communication error in case of address conflicts
• PSPNMV3-466: The GET_NUM_CONFIGURED_OBJECT service seems to give the number of maximal supported IOCR and AR, not the number of actually configured.
• PSPNMV3-465: Several fields in PNM_AP_CFG_GET_IOCR_CNF_T data are not properly initialized / zeroed as described in the API documentation.
• PSPNMV3-463: Parameters of Get Logbook Service request are not validated
• PSPNMV3-461: Check parameters in Alarm Acknowledge Service Request
• PSPNMV3-459: The Diagnosis alarm transmitted to controller by the device are not fully forwarded to the application.
• PSPNMV3-442: [NXLFW]: generic tag to disable UART and USB diagnosis is missing
• PSPNMV3-441: [cifX] SlotId is cleared after System Start
• PSPNMV3-439: Upload & Retrival Alarms are automatically handled by firmware even if automatic alarm handling for this alarm type is disabled
• PSPNMV3-437: Communication errors in Netload Class III Normal Scenario
• PSPNMV3-434: [loadable module]: ReadImplicit service not working as expected (always returns ulPnio 0xFFFFFFFF)
• PSPNMV3-427: handling of multiple DCP Set Signal Indication via mailbox may block mailbox handling
• PSPNMV3-426: Unexpected packet status in DCP Set Indication
• PSPNMV3-425: Wrong packet length in DCP Set Indication
• PSPNMV3-423: wrong value in field ulExt of confirmation for last fragmented LoadRemanent Request
• PSPNMV3-422: Confirmation for Bus on is delayed
• PSPNMV3-406: RCX_GET_DPM_IO_INFO_REQ reports wrong IO data length
• PSPNMV3-402: Update PSDCERPCV5 to V5.2.0.3
• PSPNMV3-400: Sending DCP Factory Reset using old encoding not possible
• PSPNMV3-394: First two data bytes of PNIO_APCTL_CMD_WRITE_REQ set to zero
• PSPNMV3-388: LED Still blinking after clearing Watchdog Error by Channel Init
• PSPNMV3-387: Update PSDCERPC to V5.1.0.3
• PSPNMV3-386: Update external PSLWIP to V3.2.0.3
• PSPNMV3-381: DCP Hello test fails during normal netload class III (certification issue)
• PSPNMV3-380: Legacy implicit read request does not work
• PSPNMV3-379: Unexpected LED behavior when recondiguring while address conflict detected
• PSPNMV3-377: Too slow device identify freqency
• PSPNMV3-375: Update to PSDRVETH V1.3.0.1
• PSPNMV3-373: Connection via USB or UART unstable
• PSPNMV3-372: ulDiagFlags in service RCX_GET_SLAVE_CONN_INFO_REQ are not updated for all possible failures of configured IO Device
• PSPNMV3-369: DA-AR stuck in endless loop
• PSPNMV3-368: Garbage data delivered by Get Logbook Service
• PSPNMV3-367: BF LED behavior wrong in case of Bus OFF
• PSPNMV3-363: Configuration error set at runtime
• PSPNMV3-356: invalid characters used in DCP Identify Request
• PSPNMV3-349: Negative fragmented packet status may be ignored by the firmware
• PSPNMV3-328: Session monitoring not activated for Legacy Startup Mode

Version V3.2.2.0

Changes:

• PSPNMV3-492: update to EthernetInterface V4.5.0.1

Bugs:

• PSPNMV3-491: Invalid FrameSendOffset in IOCR block for non IRT IOCR
• PSPNMV3-486: IP address conflict not cleared by Channel Init or Start Stop Communication service
• PSPNMV3-482: Wrong SlaveState (OK) in MasterStatusBlock if an IO Device has reported a fault
• PSPNMV3-479: Service DCP Get is rejected if MAC Address shall be read
• PSPNMV3-477: sometimes no LinkStatus Indication generated to registered application on LinkDown
• PSPNMV3-476: Sometimes COM-Flag not cleared even when all network cables are removed
• PSPNMV3-475: Get basic parameter service returns wrong DPM Watchdog time
• PSPNMV3-474: Some Alarm Acknowledge Request parameters are not checked for plausability
• PSPNMV3-473: Reject Alarm Acknowledge Request before Alarm Response
• PSPNMV3-471: Invalid led state and Communication error in case of address conflicts
• PSPNMV3-466: The GET_NUM_CONFIGURED_OBJECT service seems to give the number of maximal supported IOCR and AR, not the number of actually configured.
• PSPNMV3-465: Several fields in PNM_AP_CFG_GET_IOCR_CNF_T data are not properly initialized / zeroed as described in the API documentation.
• PSPNMV3-463: Parameters of Get Logbook Service request are not validated
• PSPNMV3-461: Check parameters in Alarm Acknowledge Service Request
• PSPNMV3-459: The Diagnosis alarm transmitted to controller by the device are not fully forwarded to the application.

Version V3.2.1.0

Version V3.2.0.5

Changes:

• PSPNMV3-516: Update Profinet Core to V1.4.0.7
• PSPNMV3-444: DCP Identify Response field IPOptions.BlockInfo shall be ignored

Bugs:

• PSPNMV3-505: Invalid encoding of PDInterfaceMRPDataAdjust V1.1 record
• PSPNMV3-504: Unexpected IP address conflict detection match
• PSPNMV3-503: Legacy Bus Scan Method might return wrong device information
• PSPNMV3-499: Unexpected packet length for failed Read Implicit Record service response

Version V3.2.0.4

Changes:

• PSPNMV3-438: Update PSPNCORE to V1.4.0.6

Bugs:

• PSPNMV3-441: [cifX] SlotId is cleared after System Start
• PSPNMV3-439: Upload & Retrival Alarms are automatically handled by firmware even if automatic alarm handling for this alarm type is disabled
• PSPNMV3-437: Communication errors in Netload Class III Normal Scenario

Version V3.2.0.3

Bugs:

• PSPNMV3-434: [loadable module]: ReadImplicit service not working as expected (always returns ulPnio 0xFFFFFFFF)

Version V3.2.0.2

Changes:

• PSPNMV3-430: RCX_UNREGISTER_APP_REQ is not accepted by firmware in some cases (e.g. using TCP Server)
• PSPNMV3-428: Update to LLDP V5.1.0.2

Bugs:

• PSPNMV3-432: Update to PSPNCORE V1.4.0.5
• PSPNMV3-427: handling of multiple DCP Set Signal Indication via mailbox may block mailbox handling
• PSPNMV3-426: Unexpected packet status in DCP Set Indication
• PSPNMV3-425: Wrong packet length in DCP Set Indication
• PSPNMV3-406: RCX_GET_DPM_IO_INFO_REQ reports wrong IO data length
• PSPNMV3-388: LED Still blinking after clearing Watchdog Error by Channel Init

Version V3.2.0.1

New Features:

• PSPNMV3-399: Feature: Allow to read PDRealData on local Port- and Interfacesubmodules
• PSPNMV3-395: Feature: Add taglist to modify firmware identification parameters

Changes:

• PSPNMV3-404: update to ConfigManager V1.0.2.0
• PSPNMV3-401: Update PSDCERPCV5 to V5.1.0.4
• PSPNMV3-390: Update PSLWIP to V3.2.0.5
• PSPNMV3-389: Update PSLLDPV5 to V5.1.0.1

Bugs:

• PSPNMV3-400: Sending DCP Factory Reset using old encoding not possible
• PSPNMV3-394: First two data bytes of PNIO_APCTL_CMD_WRITE_REQ set to zero

Version V3.2.0.0

New Features:

• PSPNMV3-337: Add check for mixed multiple interface mode
• PSPNMV3-316: implement check of MRP Manager License Bit in SecMem and error handling in case of missing license
• PSPNMV3-314: Feature: Add API to modify automatic alarm handling independend from configuration
• PSPNMV3-307: add API to read out the whole firmware configuration (including DPM layout)
• PSPNMV3-295: Implement mechanism to indicate / receive remanent data to / from host application
• PSPNMV3-294: extend configuration API to contain the calculated values for IsoM IO Controller application
• PSPNMV3-289: Feature: Add API to configure which IP to use for AR (given by engineering or found in network)
• PSPNMV3-232: Feature: Add support for Read/Write record services with up to 16588 byte record length

Changes:

• PSPNMV3-378: Introduce timeout for IRT startup
• PSPNMV3-364: add a new flag that is set in case a submodule with diagnosis is reported in ModuleDiffBlock
• PSPNMV3-354: configuration packets with higher StructVersion shall be acceptedby the firmware if technically possible
• PSPNMV3-351: update to PN Core 1.4.0.2
• PSPNMV3-340: in case no port offers 100MBit/s FullDuplex no AR shall be established
• PSPNMV3-338: update several external components (e.g. several Toolboxes)
• PSPNMV3-310: Reject invalid MRP Domain name setting

Bugs:

• PSPNMV3-387: Update PSDCERPC to V5.1.0.3
• PSPNMV3-386: Update external PSLWIP to V3.2.0.3
• PSPNMV3-383: Update to PSPNCORE V1.4.0.3
• PSPNMV3-381: DCP Hello test fails during normal netload class III (certification issue)
• PSPNMV3-380: Legacy implicit read request does not work
• PSPNMV3-379: Unexpected LED behavior when recondiguring while address conflict detected
• PSPNMV3-377: Too slow device identify freqency
• PSPNMV3-375: Update to PSDRVETH V1.3.0.1
• PSPNMV3-373: Connection via USB or UART unstable
• PSPNMV3-372: ulDiagFlags in service RCX_GET_SLAVE_CONN_INFO_REQ are not updated for all possible failures of configured IO Device
• PSPNMV3-369: DA-AR stuck in endless loop
• PSPNMV3-368: Garbage data delivered by Get Logbook Service
• PSPNMV3-367: BF LED behavior wrong in case of Bus OFF
• PSPNMV3-363: Configuration error set at runtime
• PSPNMV3-356: invalid characters used in DCP Identify Request
• PSPNMV3-352: Feature: Add API for application to be able to modify VendorID and DeviceID
• PSPNMV3-349: Negative fragmented packet status may be ignored by the firmware
• PSPNMV3-347: Update PSDCERPC to V5.1.0.1
• PSPNMV3-345: IP configuration fault is not detected
• PSPNMV3-344: In case a DPM Watchdogerror occurrs this is not always reported in DPM ulCommunicationError
• PSPNMV3-341: invalid (old) IO Data sent to network after configuration is changed
• PSPNMV3-336: Wrong error returned when DCP DeviceInitiative requested.
• PSPNMV3-335: Invalid OrderId reported
• PSPNMV3-334: Multiple write request with wrong sequence number when FSU enabled
• PSPNMV3-331: Controller generates unexpected Multiple Write request
• PSPNMV3-328: Session monitoring not activated for Legacy Startup Mode
• PSPNMV3-325: MasterStatusBlock SlaveState is not handled correctly
• PSPNMV3-322: wrong coded DCP Identify Request sent after configuration
• PSPNMV3-320: RPC trigger index is read during AR establishment even for legacy startup
• PSPNMV3-311: PPM active after RTA error PDU
• PSPNMV3-309: Submodule after plug not parameterized
• PSPNMV3-305: configured firmware where configuration contains no IO Devices reports Connection timeout error
• PSPNMV3-304: legacy busscan not working as expected (returns last device found in the network twice)
• PSPNMV3-303: handling of internal diagnosis (e.g. wrong peer detected) is not working as expected
• PSPNMV3-296: wrong NameOfStation assigned automatically

Version V3.1.2.0

New Features:

• PSPNMV3-337: Add check for mixed multiple interface mode
• PSPNMV3-316: implement check of MRP Manager License Bit in SecMem and error handling in case of missing license
• PSPNMV3-314: Feature: Add API to modify automatic alarm handling independend from configuration
• PSPNMV3-307: add API to read out the whole firmware configuration (including DPM layout)
• PSPNMV3-295: Implement mechanism to indicate / receive remanent data to / from host application
• PSPNMV3-294: extend configuration API to contain the calculated values for IsoM IO Controller application
• PSPNMV3-289: Feature: Add API to configure which IP to use for AR (given by engineering or found in network)
• PSPNMV3-232: Feature: Add support for Read/Write record services with up to 16588 byte record length

Changes:

• PSPNMV3-351: update to PN Core 1.4.0.2
• PSPNMV3-340: in case no port offers 100MBit/s FullDuplex no AR shall be established
• PSPNMV3-338: update several external components (e.g. several Toolboxes)
• PSPNMV3-310: Reject invalid MRP Domain name setting

Bugs:

• PSPNMV3-349: Negative fragmented packet status may be ignored by the firmware
• PSPNMV3-345: IP configuration fault is not detected
• PSPNMV3-344: In case a DPM Watchdogerror occurrs this is not always reported in DPM ulCommunicationError
• PSPNMV3-341: invalid (old) IO Data sent to network after configuration is changed
• PSPNMV3-336: Wrong error returned when DCP DeviceInitiative requested.
• PSPNMV3-335: Invalid OrderId reported
• PSPNMV3-334: Multiple write request with wrong sequence number when FSU enabled
• PSPNMV3-331: Controller generates unexpected Multiple Write request
• PSPNMV3-328: Session monitoring not activated for Legacy Startup Mode
• PSPNMV3-325: MasterStatusBlock SlaveState is not handled correctly
• PSPNMV3-322: wrong coded DCP Identify Request sent after configuration
• PSPNMV3-320: RPC trigger index is read during AR establishment even for legacy startup
• PSPNMV3-311: PPM active after RTA error PDU
• PSPNMV3-309: Submodule after plug not parameterized
• PSPNMV3-305: configured firmware where configuration contains no IO Devices reports Connection timeout error
• PSPNMV3-304: legacy busscan not working as expected (returns last device found in the network twice)
• PSPNMV3-296: wrong NameOfStation assigned automatically

Version V3.1.1.0

New Features:

• PSPNMV3-286: Feature: Add local Profinet IO Controller cycle counter to DPM Input area
• PSPNMV3-285: Feature: Add API to be able to use IO Devices with Isochroneous Mode
• PSPNMV3-196: Integrate MRP Manager

Changes:

• PSPNMV3-302: Update Profinet Core to V1.3.1.0
• PSPNMV3-300: Introduce HAL Toolbox V1.0.0.0
• PSPNMV3-283: Adapt to PSPNCORE diagnosis database changes

Bugs:

• PSPNMV3-297: Update to LLDP V5.0.17.0
• PSPNMV3-292: Multiple interface mode not implemented
• PSPNMV3-282: Hilscher netIdent protocol not active
• PSPNMV3-281: AR resource deadlock when RPC Release.req not responded by device
• PSPNMV3-279: Address conflict detection not working as expected
• PSPNMV3-278: Invalid NameOfStation in PNIO_APCTL_CMD_DCP_IDENT_IND (Legacy Bus Scan)
• PSPNMV3-276: Update to LwIP V3.1.0.2

Version V3.1.0.1

Bugs:

• PSPNMV3-281: AR resource deadlock when RPC Release.req not responded by device
• PSPNMV3-279: Address conflict detection not working as expected
• PSPNMV3-278: Invalid NameOfStation in PNIO_APCTL_CMD_DCP_IDENT_IND (Legacy Bus Scan)
• PSPNMV3-276: Update to LwIP V3.1.0.2
• PSPNMV3-273: Update to Profinet Core V1.3.0.2

Version V3.1.0.0

New Features:

• PSPNMV3-239: add API for Supervisor DA AR
• PSPNMV3-228: add possibility for application to get information if IO Controller locally has a diagnosis (e.g. wrong neighbor is detected)

Bugs:

• PSPNMV3-277: Socket Api headers not distributed
• PSPNMV3-275: [NJ100]: UART not working
• PSPNMV3-274: [comX100]: UART not working
• PSPNMV3-271: Portsubmodules with more than one digit not supported.
• PSPNMV3-269: MauType Difference Mode activated if PDPortDataCheck configured
• PSPNMV3-268: Multiple Diagnosis Data in one Alarm are not supported
• PSPNMV3-267: Invalid values for Name of Station accepted by Establish DA-AR Service
• PSPNMV3-266: Invalid DA-AR IP configuration accepted
• PSPNMV3-265: Invalid source mac address in application DCP services
• PSPNMV3-264: AR deadlock if DCERPC transfer error occurs in RPCConnect.req()
• PSPNMV3-262: DCERPC Transfer Status ignored.
• PSPNMV3-257: Firmware crash/unresponsible when using xChannelBusState and xChannelReset
• PSPNMV3-250: Confirmation for Bus on is delayed
• PSPNMV3-233: No RPC Release Service used when connection is terminated